Robustness testing is any quality assurance methodology focused on testing the robustness of software. Robustness testing has also been used to describe the process of verifying the robustness (i.e. correctness) of test cases in a test process.
ANSI and IEEE have defined robustness as the degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions.[1]
The term "robustness testing" was first used by the Ballista project at Carnegie Mellon University. They performed testing of operating systems for dependability based on the data types of POSIX API, producing complete system crashes in some systems. [2] The term was also used by OUSPG and VTT researchers taking part in the PROTOS project in the context of software security testing.[3] Eventually the term Fuzzing (which security people use for mostly non-intelligent and random robustness testing) extended to also cover model-based robustness testing.
List of tools for robustness testing is maintained e.g. here: http://www.protocoltesting.com/robustness.html (link is dead)
An overview of robustness testing methods and tools can be found in the state of the art report[4] of the AMBER research project.